Explain cancelled CLI deprecations clearly #5864
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What was the end-user or developer problem that led to this PR?
Cancelled CLI deprecations in 2019 just before the release of Bundler 2.1.0 have been hard to understand and 3 years passed after.
Especially an introduction of
bundle config
new subcommand-based interface (rubygems/bundler#7561) was not postponed.What is your fix for the problem, implemented in this PR?
bundle config
.Updates rubygems/bundler#7561
Make sure the following tasks are checked
Resources
bundle config
andbundle update
without args bundler#7475Signed-off-by: Takuya Noguchi takninnovationresearch@gmail.com